Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

…chema

Addresses Cursor Bugbot review on PR superplanehq#5763: claude.textPrompt Setup only
checked the schema root was an object, while the field description and docs
require every object to set additionalProperties:false (an Anthropic
requirement). Such schemas passed Setup and failed later at the Claude API,
unlike openai.textPrompt which rejects them at Setup.

Add validateClaudeOutputSchema: a recursive check that every object sets
additionalProperties:false (walking properties, items, anyOf/allOf/oneOf,
$defs). It intentionally does NOT require all properties in "required" —
Anthropic permits optional fields, unlike OpenAI strict mode.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

Replace the raw JSON Schema input on claude.textPrompt and openai.textPrompt
with a guided builder: users define output fields (name, type, description,
required) including nested objects and lists, and the backend assembles the
JSON Schema. Provider rules are handled automatically -- Anthropic omits
optional fields from "required"; OpenAI strict mode lists every field and
makes optional ones nullable. Shared logic lives in the new
pkg/integrations/structuredoutput package.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

Enabling a togglable field only stored its value in local state until a
save-on-blur field type (e.g. a text field pre-filled with a default) was
blurred. A run or reload before that persisted config without the value, so a
component like the structured-output schema showed as enabled but was silently
skipped. Trigger autosave on the off->on transition of a togglable field.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

The canvas node tile computed the badge as
meta?.structuredOutput ?? hasSchema(config?.outputSchema), so a stale persisted
metadata flag (autosave updates configuration only) kept the badge visible after
structured output was cleared or disabled. Derive it from the live configuration
instead, falling back to metadata only when no configuration is present.

Also run prettier on SettingsTab.tsx so make check.format.js passes.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

The structured-output helpers build configuration fields and JSON schemas for
integrations rather than being an integration themselves, so per review they do
not belong under pkg/integrations. Move the package to
pkg/configuration/structuredoutput (alongside the existing
pkg/configuration/expressionvalidation helper) and update the claude and openai
text prompt imports.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>

The structured-output schema field supports expressions like the prompt field,
but Setup parsed the stored value as literal JSON, so a schema containing an
unresolved {{ ... }} expression failed config-time validation even though it
would resolve to valid JSON at execution. Skip JSON validation in Setup when the
schema still contains an expression; Execute re-parses the resolved value.

Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>